Skip to content

Updating alerting aliases to be hidden #237534

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 12 commits into
base: main
Choose a base branch
from
Draft

Updating alerting aliases to be hidden #237534

wants to merge 12 commits into from
+257 −36

Conversation

doakalexi
Copy link
Contributor

Summary

Summarize your PR. If it involves visual changes include a screenshot or gif.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 3, 2025 •
edited
Loading

🤖 Jobs for this PR can be triggered through checkboxes. 🚧

ℹ️ To trigger the CI, please tick the checkbox below 👇

  • Click to trigger kibana-pull-request for this PR!
  • Click to trigger kibana-deploy-project-from-pr for this PR!
  • Click to trigger kibana-deploy-cloud-from-pr for this PR!

kibanamachine and others added 11 commits October 3, 2025 20:04
@kibanamachine
[CI] Auto-commit changed files from 'node scripts/eslint_all_files --…
df3bd8f 
…no-cache --fix'
@doakalexi
Fixing linting error
b7b3a7f
@doakalexi
Merge branch 'alerting/set-aliases-to-be-hidden' of github.com:doakal…
9cf2fce 
…exi/kibana into alerting/set-aliases-to-be-hidden
@doakalexi
Merge branch 'main' into alerting/set-aliases-to-be-hidden
a780a4e
@doakalexi
Merge branch 'main' into alerting/set-aliases-to-be-hidden
f92d1fa
@doakalexi
Fixing more tests
db9173a
@doakalexi
Merge branch 'alerting/set-aliases-to-be-hidden' of github.com:doakal…
cc26496 
…exi/kibana into alerting/set-aliases-to-be-hidden
@doakalexi
Merge branch 'main' of github.com:elastic/kibana into alerting/set-al…
e2ace73 
…iases-to-be-hidden
@doakalexi
Merge branch 'main' into alerting/set-aliases-to-be-hidden
5c379e0
@doakalexi
Fixing more tests
a3d88e7
@doakalexi
Merge branch 'alerting/set-aliases-to-be-hidden' of github.com:doakal…
a9f1c6b 
…exi/kibana into alerting/set-aliases-to-be-hidden
@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 21, 2025 •
edited
Loading

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #79 / Alerts and alerts index related logic - Basic License/Essentials Tier ESS specific alerts and alert index logic ESS specific alerts index migration logic @ess Creating signals migrations "after each" hook for "returns the information necessary to finalize the migration"
  • [job] [logs] FTR Configs #79 / Alerts and alerts index related logic - Basic License/Essentials Tier ESS specific alerts and alert index logic ESS specific alerts index migration logic @ess Creating signals migrations "after each" hook for "returns the information necessary to finalize the migration"
  • [job] [logs] FTR Configs #79 / Alerts and alerts index related logic - Basic License/Essentials Tier ESS specific alerts and alert index logic ESS specific alerts index migration logic @ess Creating signals migrations returns the information necessary to finalize the migration
  • [job] [logs] FTR Configs #79 / Alerts and alerts index related logic - Basic License/Essentials Tier ESS specific alerts and alert index logic ESS specific alerts index migration logic @ess Creating signals migrations returns the information necessary to finalize the migration
  • [job] [logs] FTR Configs #47 / Fleet packages test Automatic agent upgrades "after all" hook for "should take agents marked and ready for retry into account and upgrade them"
  • [job] [logs] FTR Configs #47 / Fleet packages test Automatic agent upgrades should take agents marked and ready for retry into account and upgrade them
  • [job] [logs] FTR Configs #2 / Maps endpoints apis search ES|QL should return getValues response in expected shape
  • [job] [logs] FTR Configs #2 / Maps endpoints apis search ES|QL should return getValues response in expected shape
  • [job] [logs] FTR Configs #22 / Session View API (basic) Session view - /internal/session_view/process_events - with a basic license using typical process event data "before all" hook for "/internal/session_view/process_events fails when an invalid api version is specified"
  • [job] [logs] FTR Configs #22 / Session View API (basic) Session view - /internal/session_view/process_events - with a basic license using typical process event data "before all" hook for "/internal/session_view/process_events fails when an invalid api version is specified"

Metrics [docs]

✅ unchanged

History

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@doakalexi @elasticmachine @kibanamachine